Guide Studio authoring and reviewed deployment operations - #9

Studio now guides workflow authors through step settings, AI connections, reusable actions, and deployment configuration. Editor commands are aligned, sidebars are organized and searchable, field-specific source choices include accessible help, and invalid or unapplied edits remain visible. Existing project actions and creating a new API action have distinct entry points. Studio can recover its session from temporary admission pressure while page assets load independently of busy platform calls.

Operators can register existing container destinations, import observed resources, select admitted worker releases, review and approve immutable plans, and apply changes through an outbound runner. Compose uses trusted templates; Kubernetes and Azure Container Apps support bounded changes to existing resources. Provider credentials and resource/image limits stay beside the destination. Cloud cluster provisioning remains external, and the API scheduler remains a singleton.

Worker details expose dated contact, capacity, and revision-checked drain/resume without revoking active leases. Lumi can explain explicitly selected Operations records with permission-checked, bounded context; it cannot apply infrastructure changes. Compatibility monitor health now detects stopped or stalled scans. Unsupported deployment changes are rejected before plan approval.

Includes migrations 0029_deployments and 0030_worker_presence, scoped Operations roles, illustrated English guides, core alpha12, and worker packages 0.1.4. Existing workflow roles gain no infrastructure authority.

Validation: all 17 normal gates passed for the final package, including 3,622 core unit/contract tests, worker tests, lint/types/docs, builds, and clean installed package closures. Studio passed 653 unit tests and 914 browser tests; six opt-in live authentication cases were not run. The final package passed all four queue scenarios: 400 successful tasks, 400 recorded effects, and no task retries.

Integration coverage accounts for all 629 current cases: 94 affected cases rerun on the final package plus 535 unchanged cases from reviewed prior evidence. Process coverage accounts for all 69 current cases: 17 rerun on the final package plus 52 unchanged recovery cases using the direct HTTP protocol. This is explicit incremental coverage, not a single canonical release run. The only package changes since the prior completed evidence are the two SDK renewal modules; package inventories, source/fixture hashes, and exact passing-case sets are checked. Earlier failed receipts are retained.

Real Studio/API/runner/SDK acceptance proved worker registration, one business task and heartbeat, followed by a reviewed restart, drain, and scale-to-zero lifecycle. Fresh final-package native/worker integration supplements the retained unchanged Studio/runner journey. Both current and published-alpha11 restores passed against the final package. The local macOS bundle passed all eight frozen-host/build/signature checks; 14 publication assets were independently verified, including a fresh installed Studio and exact source archive.

The SDK fix keeps renewal alive through explicit capacity rejections within current lease authority. Regression tests cover single handler execution, identical retry bytes, task ownership, expiration, cancellation, and refusal to replay ambiguous outcomes. Desktop artifacts remain unsigned/ad-hoc and not notarized. Publication and Azure deployment are separate delivery steps after this PR.